Wait_Flag	
This flag determines whether PLC will wait until the device serial ports receive the intended data before continuing. The request can either send a message and wait for a reply, or send a message and continue without waiting for a reply. If the Command Block specifies that the program will not wait for a reply, the Command Block contents are sent to the device and ladder program execution resumes immediately. This is referred to as NOWAIT mode. If the Command Block specifies that the program will wait for a reply, the Command Block contents are sent to the targeted device and the CPU waits for a reply for a maximum length of time specified in the Command Block. If the device does not respond in that time, ladder program execution resumes. This is referred to as WAIT mode.
#END#

Idle_Tmout	
The idle timeout value is the maximum time the PLC waits for the device to acknowledge receipt of the request. For NOWAIT, this value is not used. (Any timeout value is ignored; it can be zero.) If WAIT is selected, this word specifies the idle timeout period, in 100-microsecond increments.
#END# 

Max_Comm_Tm	
This word contains the maximum amount of time the program should hold the window open when the device is busy. For NOWAIT, this value is not used. (Any timeout value is ignored; it can be zero.) If WAIT is selected, this word specifies the maximum time in 100 microsecond increments.
#END#

Dev_Tasks
The configuration COMMREQ defines whether the NCM is used as a DeviceNet Master, a DevceNet Slave, or as both simultaneously. It specifies the network address and data rate of the NCM. It also specifies the network address of each device, the I/O mode, and the lengths of each slaves data. The sum of the I/O data for each slave device (including the NCM itself, if the NCM is a Slave) and the 64 bits of Communications Status Data must exactly equal the length for each reference type entered using the configuration software.
Reference: VersaMax System DeviceNet Communications Modules User's Manual GFK-1533.
#END#

NCM_Task_Id
Always 0
#END#

NCM Config As DeviceNet Master
When configuring the NCM as a Master, the COMMREQ must specify:
1.	The network address of the Master.
2.	The network data rate of the Master.
3.	For each subordinate slave:
a.	Its network address
b.	Its I/O mode
c.	The amount of I/O data of each type: I, AI, Q, AQ
#END#

NCM Config As DeviceNet Slave
When configuring the NCM as a Slave, the COMMREQ must specify:
1.	The network address,
2.	The network data rate 
3.	The network mode
4.	The amount of I/O data of each type: I, AI, Q, AQ
#END#

NCM Config As DeviceNet Master And Slave Combined
When configuring the NCM as both a DeviceNet Master and Slave, COMMREQ must provide all of the configuration information for both a Master & Slave. Note that in this combined scenario, network mode of slave is ignored as Master configuration requires slave to be UCMM-capable.
1.	Network address of the Master/Slave
2.	Network data rate of Master/Slave
3.	For NCM as a Slave the amount of I/O data of each reference
4.	Type: I, AI, Q, AQ
5.	For each subordinate slave
a.	Network address
b.	I/O mode
c.	Amount of I/O data of each type: I, AI, Q, AQ
#END#

Data_Block_Len
Not Available
#END#

Command_Word	
Not Available
#END#

Master_Address	
Address of Master device
#END#

Master_Baud_Rate	
Baud Rate of Master
#END#

Number_Of_Slaves	
Number_Of_Slaves
#END#

Slave_Address	
Address of Slave
#END#

Slave_IO_Mode	
I/O mode of Slave
#END#

Slave_I_Data_Length	
I data length of Slave in bits
#END#

Slave_AI_Data_Length	
AI data length of Slave in words
#END#

Slave_Q_Data_Length	
Q data length of Slave in bits
#END#

Slave_AQ_Data_Length
AQ data length of Slave in words
#END#

Length_Of_I
Length_Of_I
#END#

Length_Of_AI
Length_Of_AI
#END#

Length_Of_Q
Length_Of_Q	
#END#

Length_Of_AQ
Length_Of_AQ	
#END#

NCM_Slave_Comm_Mode
In the Master case, the NCM Slave communication mode is fixed as UCMM-capable.
#END#
